\ \(em\ This element must be present when ControlInfo is conveyed by a
normal document and more than one TAPDU are conveyed in this session.
.LP
\fINote\ 2\fR
\ \(em\ OR Descriptor must contain an ORAddress and at least one of
these addresses must be present.
.LP
\fINote\ 3\fR
\ \(em\ When this element is omitted, the TLMAU shall construct this
component which consists of the following components: originator name,
date and time, and if necessary, a sequence number.
.LP
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [3T21.330], p.4\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
10.1.1.2\ \ \fISendAck\(hyTAPDU\fR
.sp 9p
.RT
.PP
The SendAck\(hyTAPDU comprises following elements:
.RT
.ce
.LP
.ce
\fBH.T. [T22.330]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(228p) .
.T&
cw(228p) .
{
SendAck\(hyTAPDU
SendAck\(hyTAPDU ::= SEQUENCE\ { |
.LP
\fBSend\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::=\fR
sendAck [0] SendAckTAPDUId,
.LP
\fBSend ::= sendAck\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \fR
correlationInfo
CorrelationInfoElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \fR
\ call\(hyid
CallIdentification\ } }
.LP
\(hy\(hy\ \fISee Note\fR
.LP
\fBSend\fR
[1] SET\ { |
.LP
\fBSend ::= send\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \fR
submissionId
SubmissionIdElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \fR
\ submission\(hymsg\(hyid
MessageIdentifier\ }
.LP
\fBSend ::= send\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \fR
submissionTime
SubmissionTimeElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \fR
\ submission\(hytime
DateandTime\ } } }
.LP
}
_
.T&
cw(228p) .
{
\ \
\fINote\fR
\ \(em\ This element is a session connection information that identifies
previous Send\(hyTAPDU being reported\ on.
.LP
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T22.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 1
.sp 1P
.LP
10.1.1.3\ \ \fIException\(hyTAPDU\fR
.sp 9p
.RT
.PP
The Exception\(hyTAPDU comprises following elements:
.RT
.ce
.LP
.ce
\fBH.T. [T23.330]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(228p) .
.T&
cw(228p) .
{
Exception\(hyTAPDU
Exception\(hyTAPDU ::= SEQUENCE\ { |
.LP
\fBSend\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::=\fR
exception [0] ExceptionTAPDUId,
.LP
\fBSend ::= exception\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \fR
correlationInfo
CorrelationInfoElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \fR
\ call\(hyid
CallIdentification\ }
.LP
\(hy\(hy\ \fISee Note\fR
.LP
\fBSend ::= exception\fR
[2] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \fR
errors
ErrorsElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \fR
\ error\(hycause
ErrorCauseValue\ } } }
.LP
}
_
.T&
cw(228p) .
{
\ \
\fINote\fR
\ \(em\ This element is a session connection information that identifies
associated TAPDU being reported on e.g.\ Send\(hyTAPDU.
.LP
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T23.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
10.1.2
\fIMessageProbe\fR
.sp 9p
.RT
.PP
A TLM terminal sends a Probe\(hyTAPDU to invoke the MessageProbe
abstract operation. The TLMAU returns a ProbeAck\(hyTAPDU to report the
result of that operation, or may return an Exception\(hyTAPDU (\(sc\ 10.1.1.3)
to report an
abstract error.
.RT
.sp 1P
.LP
10.1.2.1\ \ \fIProbe\(hyTAPDU\fR
.sp 9p
.RT
.PP
The Probe\(hyTAPDU comprises following elements:
.RT
.ce
.LP
.ce
\fBH.T. [T24.330]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(228p) .
.T&
cw(228p) .
{
Probe\(hyTAPDU
Probe\(hyTAPDU ::= SEQUENCE\ { |
.LP
\fBSend\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::=\fR
probe [0] ProbeTAPDUId,
.LP
\fBSend ::= probe\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \fR
quantityOfDocs
QuantityOfDocsElementId,
.LP
\fBSend ::= S [0]\ \ \ \fR
\ number\(hyof\(hydocs
NumberOfAssociatedDocuments\ } | PTIONAL\ }
.LP
\fBSend\fR
[1] SET\ { |
.LP
\fBSend [1] SET\ { | fR
\(hy\(hy\ \fIContinuation see send\(hyTAPDU\fR
.
.LP
\fBSend [1] SET\ { | fR
\(hy\(hy\ \fINote that only few elements of the send\(hyTAPDU are relevant for\fR
\fIa Probe\(hyTAPDU\fR
.
.LP
\fBSend [1] SET\ { | fR
\(hy\(hy\ \fINot relevant elements will be ignored\fR
.
.LP
\fBSend [1] SET\ { | fR
\(hy\(hy\ \fIAt least one recipient must be present\fR
.
}
_
.T&
cw(228p) .
\ \
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T24.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 3
.sp 1P
.LP
10.1.2.2\ \ \fIProbeAck\(hyTAPDU\fR
.sp 9p
.RT
.PP
The ProbeAck\(hyTAPDU comprises following elements:
.RT
.ce
.LP
.ce
\fBH.T. [T25.330]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(228p) .
.T&
cw(228p) .
{
ProbeAck\(hyTAPDU
ProbeAck\(hyTAPDU ::= SEQUENCE\ { |
.LP
\fBSend\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::=\fR
probeAck [0] ProbeAckTAPDUId,
.LP
\fBSend ::= probeAck\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \fR
correlationInfo
CorrelationInfoElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \fR
\ call\(hyid
CallIdentification\ } }
.LP
\fBSend\fR
[1] SET\ { |
.LP
\fBSend ::= send\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \fR
probeId
ProbeElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \fR
\ probe\(hymsg\(hyid
MessageIdentifier\ }
.LP
\fBSend ::= send\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \fR
submissionTime
SubmissionTimeElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \fR
\ submission\(hytime
DateandTime\ } } }
}
_
.T&
cw(228p) .
\ \
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T25.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
10.1.3
\fIExplicitReceive\fR
.sp 9p
.RT
.PP
A TLM terminal sends an ExplicitRN\(hyTAPDU to invoke the
ExplicitReceive abstract operation. The TLMAU returns an ExplicitRNAck\(hyTAPDU
to report the result of that operation, or may return an Exception\(hyTAPDU
(see
\(sc\ 10.1.1.3), to report an abstract error.
.RT
.sp 1P
.LP
10.1.3.1\ \ \fIExplicitRN\(hyTAPDU\fR
.sp 9p
.RT
.PP
The ExplicitRN\(hyTAPDU comprises following elements:
.RT
.ce
.LP
.ce
\fBH.T. [T26.330]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(228p) .
.T&
cw(228p) .
{
ExplicitRN\(hyTAPDU
ExplicitRN\(hyTAPDU ::= SEQUENCE\ { |
.LP
\fBSend\fR
[0]
.LP
\fBSend ::= S [0]\ \ \fR
explicitRN
ExplicitRNTAPDUId,
.LP
\fBSend\fR
[1] SET\ { |
.LP
\fBSend ::= send\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \fR
recipients
RecipientsElementId,
.LP
\fBSend ::= S [0]\ \ \fR
\ recipient\(hyname
ORName\ }
.LP
\fBSend ::= send\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \fR
priority
PriorityElementId,
.LP
\fBSend ::= S [0]\ \ \fR
\ priority\(hyind
PriorityValue DEFAULT normal\ } | PTIONAL,
.LP
\fBSend ::= send\fR
[2] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \fR
subjectIPM
SubjectIPMElementId,
.LP
\fBSend ::= S [0]\ \ \fR
\ subject\(hyipm\(hyid
IPMIdentifier\ } | PTIONAL,
.LP
\fBSend ::= send\fR
[3] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \fR
IPNOriginator
IPNOriginatorElementId,
.LP
\fBSend ::= S [0]\ \ \fR
\ ipn\(hyoriginating\(hyuser
ORDescriptor\ } | PTIONAL,
.LP
\fBSend ::= send\fR
[4] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \fR
timeOfReceipt
TimeOfReceiptElementId,
.LP
\fBSend ::= S [0]\ \ \fR
\ receipt\(hytime
DateandTime\ } | PTIONAL,
.LP
\fBSend ::= send\fR
[5] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \fR
convertedInfoTypes
ConvertedInfoTypesElementId,
.LP
\fBSend ::= send [5]\fR
SET OF
.LP
\fBSend ::= S [0]\ \ \fR
eIT
EITValue\ } | PTIONAL\ } }
}
_
.T&
cw(228p) .
{
\ \
\fINote\fR
\ \(em\ If receipt\(hytime element defined in Receipt is omitted, TLMAU extracts one from the CES of the session in which this TAPDU was transferred. This may differ from the time of actual receipt of IPM.
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T26.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
10.1.3.2\ \ \fIExplicitRNAck\(hyTAPDU\fR
.sp 9p
.RT
.PP
The ExplicitRNAck\(hyTAPDU comprises following elements:
.RT
.ce
.LP
.ce
\fBH.T. [T27.330]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(228p) .
.T&
cw(228p) .
{
ExplicitRNAck\(hyTAPDU
ExplicitRN\(hyTAPDU ::= SEQUENCE\ { |
.LP
\fBSend\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::=\fR
explicitRNAck [0] ExplicitRNTAPDUId,
.LP
\fBSend ::= explicitRNAck\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \ \ \fR
correlationInfo
CorrelationInfoElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \ \ \fR
\ call\(hyid
CallIdentification\ } }
.LP
\fBSend\fR
[1] SET\ { |
.LP
\fBSend ::= send\fR
[0] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \ \ \fR
submissionId
SubmissionElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \ \fR
\ submission\(hymsg\(hyid
MessageIdentifier\ }
.LP
\fBSend ::= send\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \ \ \ \fR
submissionTime
SubmissionTimeElementId,
.LP
\fBSend ::= S [0]\ \ \ \ \ \ \fR
\ submission\(hytime
DateandTime\ } } }
}
_
.T&
cw(228p) .
\ \
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T27.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 3
.sp 1P
.LP
10.1.4
\fIMessageCancel\fR
.sp 9p
.RT
.PP
A TLM terminal sends a Cancel\(hyTAPDU to invoke the MessageCancel
abstract operation. The TLMAU returns no TAPDU to report the result of that
operation, or may return an Exception\(hyTAPDU (see \(sc\ 10.1.1.3), to
report an
abstract error.
.RT
.sp 1P
.LP
10.1.4.1\ \ \fICancel\(hyTAPDU\fR
.sp 9p
.RT
.PP
The Cancel\(hyTAPDU comprises following elements:
.RT
.ce
.LP
.ce
\fBH.T. [T28.330]\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
lw(228p) .
.T&
cw(228p) .
{
Cancel\(hyTAPDU
Cancel\(hyTAPDU ::= SEQUENCE\ { |
.LP
\fBSend ::=\fR
cancel [0] CancelTAPDUId,
.LP
\fBSend ::= cancel\fR
[1] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \fR
submissionId
SubmissionIdElementId,
.LP
\fBSend ::= S [0]\ \ \ \fR
\ submission\(hymsg\(hyid
MessageIdentifier\ } | PTIONAL,
.LP
\fBSend ::= cancel\fR
[2] SEQUENCE\ { |
.LP
\fBSend ::= S [0]\ \ \ \fR
correlation\(hyInfo
Correlation\(hyInfoElementId,
.LP
\fBSend ::= S [0]\ \ \ \fR
\ call\(hyid
CallIdentification\ } | PTIONAL\ }
.LP
\(hy\(hy\ \fIone of these must be present\fR
.
}
_
.T&
cw(228p) .
\ \
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T28.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
10.1.5
\fIMessageDeliver\fR
.sp 9p
.RT
.PP
A TLMAU sends a Deliver\(hyTAPDU to invoke the MessageDeliver abstract
operation.
.RT
.sp 1P
.LP
10.1.5.1\ \ \fIDeliver\(hyTAPDU\fR
.sp 9p
.RT
.PP
The Deliver\(hyTAPDU comprises following elements:
The section describes how the TLMAU will provide the TLM abstract service.
The TLM abstract operations have been defined by abstract operations, sometimes
with associated results or errors. These abstract operations, results and
errors are realized via the exchange of TAPDUs between the TLM terminal
and the TLMAU.
.PP
The realization of the abstract operations for the import and export ports
linking the TLMAU and the MTS, is beyond the scope of this
Recommendation. For the purpose of this section import and export operations
will be considered to be similar to submission and delivery port
operations.
.RT
.sp 1P
.LP
10.2.1
\fIMessageSend\fR
.sp 9p
.RT
.PP
The MessageSend operation will be provided by the TLMAU via the
Send\(hy, SendAck\(hy and Exception\(hyTAPDUs:
.PP
Upon receipt of Send\(hyTAPDU by the TLMAU, the TLMAU will take the
following actions:
.RT
.LP
1)
The TLMAU will invoke the MTAS import abstract operation
MessageSubmission with the following argument values:
.LP
.sp 1
.ce
\fBH.T. [T41.330]\fR
.ce
\fBSource of MTAS MessageSubmission arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(72p) | cw(36p) sw(48p) | cw(72p) , ^ | c | c | ^ .
MessageSubmission argument {
CorrespondingSend\(hyTAPDU component
} Operation
Element name Value name
_
.T&
lw(72p) | cw(36p) | cw(48p) | lw(72p) .
originator\(hyname \(em \(em {
Authenticate User (remarque 1)
}
_
.T&
lw(72p) | cw(36p) | cw(48p) | lw(72p) .
{
original\(hyencoded\(hyinformation\(hytypes
} \(em \(em {
set by TLMAU to EITs of submitted IPM's body
}
_
.T&
lw(72p) | cw(36p) | cw(48p) | lw(72p) .
content\(hytype \(em \(em set by TLMAU to \*QIPMS\*U
_
.T&
lw(72p) | cw(36p) | cw(48p) | lw(72p) .
content\(hyidentifier \(em \(em Local matter
_
.T&
lw(72p) | cw(36p) | cw(48p) | lw(72p) .
content\(hycorrelator \(em \(em Local matter
_
.T&
lw(72p) | cw(36p) | cw(48p) | lw(72p) .
recipient\(hyname to, cc, bcc {
primary\(hy, copy\(hy, blind\(hycopy\(hyrecipient
} {
constructed by TLMAU
\fINote\ 1\fR
\ \(em\ Authenticate User is constructed from TID obtained from CSS terminal ID.
.LP
\fINote\ 2\fR
\ \(em\ The IPM submitted as the content is constructed by the TLMAU.
Send\(hyTAPDU components representing IPMS elements are mapped onto the
corresponding IPMS application protocol data unit (APDU) elements.
.LP
\fINote\ 3\fR
\ \(em\ A multi\(hydocument messages will be submitted as an IP message with
a multi\(hypart body, each body part corresponding to a submitted document.
.LP
\fINote\ 4\fR
\ \(em\ When this\(hyIPM of IPMS element is omitted, the TLMAU shall construct this component which consists of the following components: originator name,
Date and Time and, if necessary, a sequence number.
.LP
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T41.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
Other message submission arguments have a corresponding Send\(hyTAPDU
component. If this component is omitted, the default value applies.
.LP
2)
If the MessageSubmission operation results in an error or if an error
is detected in the Send\(hyTAPDU, the TLMAU will return an
Exception\(hyTAPDU to the originating TLM terminal.
.LP
3)
The TLMAU will, when required, return a SendAck\(hyTAPDU to the originating
TLM terminal following the successful completion of the
MessageSubmission operation. The values of the SendAck\(hyTAPDU will be set as
follows:
.ce
\fBH.T. [T42.330]\fR
.ce
\fBSource of SendAck\(hyTAPDU components\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(42p) sw(42p) | cw(90p) , c | c | ^ .
SendAck\(hyTAPDU component Source
Element name Value name
_
.T&
lw(42p) | lw(42p) | lw(90p) .
correlationInfo call\(hyid {
CallIdentification that identifies previous Send\(hyTAPDU being
reported on
}
_
.T&
lw(42p) | lw(42p) | lw(90p) .
submissionId submission\(hymsg\(hyid {
MTS message\(hysubmission\(hyidentifier
}
_
.T&
lw(42p) | lw(42p) | lw(90p) .
submissionTime submission\(hytime {
MTS message\(hysubmission\(hytime
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T42.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
4)
The TLMAU will maintain a one\(hyto\(hyone correlation between MTS message\(hysubmission\(hyidentifiers
and correlation information values to facilitate status query.
.sp 1P
.LP
10.2.2
\fIMessageProbe\fR
.sp 9p
.RT
.PP
The MessageProbe operation is provided by the TLMAU via the Probe\(hy,
ProbeAck\(hy and Exception\(hyTAPDUs.
.PP
Upon receipt of the Probe\(hyTAPDU by the TLMAU, the TLMAU will take the
following actions:
.RT
.LP
1)
The TLMAU will invoke the MTAS import abstract operation
ProbeSubmission with the following argument values:
.LP
Source of MTAS ProbeSubmission arguments.
.LP
See \(sc 10.2.1 \(em MessageSubmission arguments.
.LP
2)
If the Probe operation results in an error or if an error is detected
in the Probe\(hyTAPDU, the TLMAN will return an Exception\(hyTAPDU to the
originator.
.LP
3)
The TLMAU will, when required, return a ProbeAck\(hyTAPDU to
the originator, following the successful completion of the probe operation.
The values of the ProbeAck\(hyTAPDU will be set as follows:
.ce
\fBH.T. [T43.330]\fR
.ce
\fBSource of ProbeAck\(hyTAPDU components\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(42p) sw(42p) | cw(90p) , c | c | ^ .
ProbeAck\(hyTAPDU component Source
Element name Value name
_
.T&
lw(42p) | lw(42p) | lw(90p) .
correlationInfo call\(hyid {
CallIdentification that identifies previous Probe\(hyTAPDU being
reported on
}
_
.T&
lw(42p) | lw(42p) | lw(90p) .
probeId probe\(hymsg\(hyid {
MTS probe\(hysubmission\(hyidentifier
}
_
.T&
lw(42p) | lw(42p) | lw(90p) .
submissionTime submission\(hytime {
MTS probe\(hysubmission\(hytime
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T43.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
10.2.3
\fIExplicitReceive\fR
.sp 9p
.RT
.PP
The ExplicitReceive operation is provided by the TLMAU via the
ExplicitRN\(hy, ExplicitRNAck\(hy and Exception\(hyTAPDUs.
.PP
Upon receipt of the ExplicitRN\(hyTAPDU the TLMAU will take the following
actions:
.RT
.LP
1)
The TLMAU will invoke the MTAS import abstract operation
MessageSubmission with the following argument values:
.LP
.sp 1
.ce
\fBH.T. [T44.330]\fR
.ce
\fBSource of MTAS MessageSubmission components\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(72p) | cw(36p) sw(30p) | cw(90p) , ^ | c | c | ^ .
MessageSubmission argument {
Corresponding ExplicitRN\(hyTAPDU component
} Operation
Element name Value name
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
originator\(hyname \(em \(em authenticate user
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
{
original\(hyencoded\(hyinformation\(hytypes
} \(em \(em {
set by TLMAU to \*Qunspecified\*U
}
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
content\(hytype \(em \(em set by TLMAU to \*QIPMS\*U
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
content\(hyidentifier \(em \(em Local matter
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
priority priority priority\(hyind
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
per\(hymessage\(hyindicators
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
\ disclose\(hyrecipients \(em \(em {
set to \*Qdisclosure\(hyof\(hyrecipient\(hyprohibited\*U
}
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
\ conversion\(hyprohibited \(em \(em {
set to \*Qconversion\(hyprohibited\*U
}
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
{
\ alternate\(hyrecipient\(hyallowed
} \(em \(em {
set to \*Qalternate\(hyrecipient\(hyprohibited\*U
}
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
{
\ content\(hyreturn\(hyrequest
} \(em \(em {
set to \*Qcontent\(hyreturn\(hynot\(hyrequested\*U
}
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
recipient\(hyname recipients recipient\(hyname
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
{
originator\(hyreport\(hyrequest
} \(em \(em {
set by TLMAU to \*Qno report\*U
}
_
.T&
lw(72p) | cw(36p) | cw(30p) | lw(90p) .
content \(em \(em {
identified as IPN
\fINote\ 1\fR
\ \(em\ The IPN submitted as the content is constructed by the TLMAU.
ExplicitRN\(hyTAPDU elements representing IPMS elements are mapped onto the
corresponding IPMS APDU elements.
.LP
\fINote\ 2\fR
\ \(em\ If receipt\(hytime is omitted, the TLMAU extracts the Receipt time from the CSS of the session in which this TAPDU was transferred to. This time may
differ from the time of actual receipt of IPM.
.LP
\fINote\ 3\fR
\ \(em\ Set acknowledgment\(hymode of IPN to \*Qmanual\*U.
.LP
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T44.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
2)
If the Message\(hySubmission operation results in an error, or if an
error is detected in the ExplicitRN\(hyTAPDU, the TLMAU will return an
Exception\(hyTAPDU to the originator.
.LP
3)
The TLMAU will, when required, return a ExplicitRNAck\(hyTAPDU to the
originator, following the successful completion of the MessageSubmission
operation. The values of the ExplicitRNAck\(hyTAPDU will be set as follows:
.LP
.sp 1
.ce
\fBH.T. [T45.330]\fR
.ce
\fBSource of ExplicitRNAck\(hyTAPDU components\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(42p) sw(42p) | cw(90p) , c | c | ^ .
{
ExplicitRNAck\(hyTAPDU component
} Source
Element name Value name
_
.T&
lw(42p) | lw(42p) | lw(90p) .
correlationInfo call\(hyid {
CallIdentification that identifies previous ExplicitRN\(hyTAPDU being
reported on
}
_
.T&
lw(42p) | lw(42p) | lw(90p) .
submissionId submission\(hymsg\(hyid {
MTS message\(hysubmission\(hyidentifier
}
_
.T&
lw(42p) | lw(42p) | lw(90p) .
submissionTime submission\(hytime {
MTS message\(hysubmission\(hytime
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T45.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 4
.sp 1P
.LP
10.2.4
\fIMessageCancel\fR
.sp 9p
.RT
.PP
The MessageCancel operation is provided by the TLMAU via the
Cancel\(hy and Exception\(hyTAPDUs.
.PP
Upon receipt of the Cancel\(hyTAPDU by the TLMAU, the TLMAU will take the
following actions:
.PP
The TLMAU will invoke the MTAS abstract operation
CancelDeferredDelivery with the following argument value:
.RT
.LP
.sp 1
.ce
\fBH.T. [T46.330]\fR
.ce
\fBSource of CancelDeferredDelivery arguments\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(72p) | cw(48p) sw(48p) | cw(60p) , ^ | c | c | ^ .
{
CancelDeferredDelivery argument
} {
Corresponding Cancel\(hyTAPDU component
} Operation
Element name Value name
_
.T&
lw(72p) | cw(48p) | cw(48p) | lw(60p) .
{
message\(hysubmission\(hyidentifier
} submissionId submission\(hymsg\(hyid
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T46.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 4
.PP
If the CancelDeferredDelivery operation results in an error, or if an error
is detected in the Cancel\(hyTAPDU, the TLMAU will return an
Exception\(hyTAPDU to the originating TLM terminal.
.bp
.sp 1P
.LP
10.2.5
\fIMessageDeliver\fR
.sp 9p
.RT
.PP
The MessageDeliver operation is provided by the TLMAU via the
Deliver\(hyTAPDU.
.PP
When the MTAS abstract operation MessageDelivery is invoked by the MTS
with an IPM as the MTS message content, the TLMAU will take the following
actions:
.RT
.LP
1)
The TLMAU will construct a Deliver\(hyTAPDU for transmission to the destination
TLM terminal with the following element values:
.ce
\fBH.T. [T47.330]\fR
.ce
\fBSource of Deliver\(hyTAPDU component\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(54p) sw(54p) | cw(72p) | cw(48p) , c | c | ^ | ^ .
Deliver\(hyTAPDU component {
Corresponding MessageDelivery argument
} Operation
Element name Value name
_
.T&
lw(54p) | lw(54p) | cw(72p) | lw(48p) .
quantityOfDocs number\(hyof\(hydocs \(em {
when control Informa
tion is conveyed by a normal document, set number of associated documents in Deliver\(hyTAPDU
\ \(em\ The IPM received by TLMAU is used to construct the Deliver\(hyTAPDU,
Deliver\(hyTAPDU elements, representing MTS and IPMS elements of service, are
constructed by the TLMAU from the MessageDeliver operation arguments and IPMS application protocol data unit (APDU) values as indicated above.
.LP
\fINote\ 2\fR
\ \(em\ Multi\(hypart body message will be sent to the destination TLM terminal by the TLMAU as a multi\(hydocument message, each document corresponding to an IP message body part.
.LP
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T47.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
2)
If the TLMAU is unable to deliver the constructed
Deliver\(hyTAPDU to the designation TLM terminal, then an IPN will be constructed
for return to the IPMS originator. This IPN will be submitted according
to
\(sc\ 10.2.6.
.LP
3)
The definition of the export port MessageDeliver abstract
operation should include a result argument indicating successful delivery or
non\(hydelivery. The MTS would then return delivery notifications to the
originators of messages routed through a TLMAU only after the result value
was indicated.
.bp
.sp 1P
.LP
10.2.6
\fIReceiptStatus Notice\fR
.sp 9p
.RT
.PP
The ReceiptStatusNotice operation is provided by the TLMAU via the ReceiptStatusNotice\(hyTAPDU.
.PP
When the MTAS abstract operation MessageDelivery is invoked by the MTS
with an IPN as the IPMS content, the TLMAU will take the following
actions:
.RT
.LP
1)
The TLMAU will construct a ReceiptStatusNotice\(hyTAPDU for
transmission to the destination TLM terminal with the following element
values:
.ce
\fBH.T. [T48.330]\fR
.ce
\fBSource of ReceiptStatusNotice\(hyTAPDU components\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(54p) sw(54p) | cw(72p) | cw(48p) , c | c | ^ | ^ .
{
ReceiptStatusNotice\(hyTAPDU component
} {
Corresponding MessageDelivery and
receive RN/NRN argument
} Operation
Element name Value name
_
.T&
lw(54p) | lw(54p) | cw(72p) | lw(48p) .
quantityOfDocs number\(hyof\(hydocs \(em {
when control Informa
tion is conveyed by a normal document, set number of associated documents\ in ReceiptStatusNotice\(hyTAPDU
\ \(em\ What is received by the TLMAU is used to construct the
ReceiptStatusNotice\(hyTAPDU. ReceiptStatusNotice\(hyTAPDU elements representing MTS and IPMS elements of service, are constructed by the TLMAU from the
MessageDeliver operation arguments and IPMS APDU values, as indicated above.
.LP
}
_
.TE
.nr PS 9
.RT
.ad r
\fBTableau [T48.330], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
10.2.7
\fIDeliveryStatusNotice\fR
.sp 9p
.RT
.PP
The DeliveryStatusNotice operations are provided by the TLMAU via the DeliveryStatusNotice\(hyTAPDU.
.PP
When the MTS abstract operation ReportDelivery is invoked by the MTS, the
TLMAU will take the following actions:
.RT
.LP
1)
The TLMAU will construct a DeliveryStatusNotice\(hyTAPDU for
transmission to the destination TLM terminal with the following element
values:
.ce
\fBH.T. [T49.330]\fR
.ce
\fBSource of DeliveryStatusNotice\(hyTAPDU components\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(54p) sw(54p) | cw(72p) | cw(48p) , c | c | ^ | ^ .
{
DeliveryStatusNotice\(hyTAPDU component
} {
Corresponding ReportDelivery argument
} Operation
Element name Value name
_
.T&
lw(54p) | lw(54p) | cw(72p) | lw(48p) .
quantityOfDocs number\(hyof\(hydocs \(em {
when control Informa
tion is conveyed by a normal document, set number of associated documents in DeliveryStatusNotice\(hyTAPDU
}
_
.T&
lw(54p) | lw(54p) | cw(72p) | lw(48p) .
correlationInfo call\(hyid \(em {
CallIdentification that identifies previous Send\(hyTAPDU being